looking at the video, great!
how can this be tested?
are there branches in plone repos using contentbrowser instead of relateditems?
or should we maybe provide an alias "relateditems" for "contentbrowser"?
i think this also needs some integration in docs.

This can be tested by using the mentioned branches of p.a.z3cform and p.a.relationfield and the webpack devel resources in the resource registry. The relationfield uses the contentbrowser widget already.

Updating all the core packages which use RelatedItemsFieldWidget isn't that hard but there are several addons which have to be updated too ... I'm not sure if its a problem when we "alias" RelatedItemsFieldWidget to ContentBrowserFieldWidget under the hood. Maybe that does work for the addons. I can give this a test ...

One more benefit from removing pat-relateditems is that we can get rid of the patched select2 3.5.x version.

Cool! Sorry I didn't read the ticket description carefully enough.

@MrTango @thet I tried to figure out the jest setup for svelte apps using this link https://www.roboleary.net/2021/11/18/svelte-app-testing-jest.html ... now I get the following message:

Jest is being called in CJS mode. You must use ESM mode in Svelte 4+

Maybe someone of you can give me a hint how to setup the testing environment?

@MrTango @petschki About sorting the selected items: What do you think about using pat-sortable from Patternslib? pat-sortable would need to be extended to make use of MutationObservers first. Currently the reinitialization only happens when a pat-update event is thrown with a added payload, which couples that pattern too tightly to internals of Patternslib, this is why I‌ think a MutationObserver should be used instead.

Ref: Patternslib/Patterns#1197

@thet Thanks for your review!

About sorting: this only gets initialized on loading the first time and doesn't work during "first time" item selection indeed. (https://github.com/plone/mockup/pull/1377/files#diff-4b241e899bfbe65a8c35ffadf58f567fea3d4df013c56306db87d1517e10798dR83) this is a small change and I will fix it asap. I'm not sure if we should use pat-sortable for this usecase.

Features:

• Multiselection is definitely on my list to implement.
• keyboard navigation too
• and restapi: yes, but this needs some more thoughts about "inplace" replacement of pat-relateditems and its options. We often use relateditems pattern as mode="search" with some additional index like portal_type=["Image", "File"] ... IMHO this should work here too ... and it's not clear to me which endpoint we should use here.

regarding keyboard navigation, yes definitely, i think i had some key's already implemented like ESC to close the browser, but i had to disabled some stuff, when i did update to Svelte 4. Not sure if is enabled already. That was a plugin.
But yeah, i want all the keyboard navigation we have in relateditems widget now and more.

regarding RestApi, here from today's classic UI meeting:

• should we use plone.restapi for the JSON endpoints?
  • talking with @MrTango, @jensens, @petschki we should do not because it should be possible to use Plone classic UI without restapi (jens mentioned circular dependency problems.)
  • the vocabulary end point in Plone core has all features we need.

and also multiselection is already on the list, even if we didn't had it before in relateditems.

btw the sorting code, we have right now is for sorting the selected items, not for sorting the items in the browser ;)
But sorting in a column would be nice to have.
Regarding global search in content browser?
- we decided to not do it, one can use ajax select widget to have this, no need to also have it here

I do not think the levels should be sortable. thats too much magic for this package.

The problem was, that initially when there are no selectedItems and you added some, they weren't sortable immediately in the field ... I've fixed that here c264843

+1 for using a different pattern for search mode. AjaxSelectFieldWidget would fit best for this.

OK ... I'll merge the current state and release another alpha of that.

Next week I'll work on :

• favorites menu
• recently used menu

and eventually :

• use @plone/registry to allow overriding components